Component tagging with maintenance related information in open and closed formats

ABSTRACT

A method for maintaining a complex article, including retrieving maintenance information relating to maintenance of a component of a complex article from an electronically-accessible tag coupled to the component and applying the retrieved maintenance information to a determination regarding maintenance of the complex article. A device including a complex article including a first component and a second component, the first and second components being one of individually replaceable and maintainable. The first component is tagged with a first tag that stores first computer accessible information including a first identifier identifying the first component and first maintenance information describing maintenance of the first component. The second component is tagged with a second tag that stores second computer accessible information including a second identifier identifying the second component and second maintenance information describing maintenance of the second component.

BACKGROUND

This invention relates to maintenance.

The tagging of articles with computer-readable identifiers andinformation has provided great improvements in areas such as supplychain management, asset tracking and management, security and accesscontrol, transportation, toll collection, baggage handling, inventorycontrol and management, healthcare, and consumer services. For example,bar codes can be used to track the storage and movement of objectsranging from foodstuffs to coupons. Radio frequency identification(“RFID”) tags can be used to track individuals as they access restrictedlocations and services. Smart cards can be used to store insuranceinformation, medical records, and phone accounts. Examples ofcomputer-readable tags include, active and passive RFID tags, integratedcircuit (“IC”) microprocessor cards and memory cards, optical memorycards, barcodes, tags, and smart cards.

SUMMARY

The present invention provides method and apparatus, includingcomputer-program products, for tagging articles with maintenance relatedinformation. Articles that can be tagged include complex articles andcomponents of complex articles. The phrase ‘complex article’ is used inthis specification to refer to tangible objects and devices that areassembled from individually taggable components. The components areindividually replaceable or maintainable on the complex article.Examples of complex articles include motor vehicles, trains, aircraft,ships, military hardware and vehicles, buildings, and assembly lines.Examples of components include engines, axels, wheels, arms, and bodyframes. Complex articles are physical incarnations formed by one or morephysical components that are amenable to being separately tagged with aunique, computer-readable identifier.

In general, in one aspect, the invention features systems and methods,and components configured to perform aspects of the methods, formaintaining complex articles. In one aspect the invention provides amethod for storing maintenance information on anelectronically-accessible tag that is coupled to an article. The methodincludes storing maintenance information in both a first and secondformat in the electronically accessible tag where the first format is inaccordance with an open standard and the second format is in accordancewith a closed standard.

Aspects of the invention can include one or more of the followingfeatures. The method can include storing maintenance information in aformat that is device independent.

Storing maintenance information in the first format can include storingthe maintenance information in a format that is in accordance with oneof RTF, ASCII, and PDF. Storing maintenance information in the secondformat includes storing the maintenance information in a format that isproprietary and that can only be accessed by proprietary devices.

The method can include retrieving the maintenance data, updating theformat of the maintenance data and storing the maintenance data with theupdated format in the electronically accessible tag. Storing maintenancedata can include storing maintenance procedures and technicalspecifications related to the article. Storing maintenance informationcan include storing a first type of maintenance information in the firstformat and storing a second type of maintenance information in thesecond format. Storing a first type of maintenance information in thefirst format includes storing maintenance logs in the first format andstoring maintenance procedures and technical specifications in thesecond format. Storing maintenance information can include storingmaintenance information of a component of one of an aircraft, a seagoing vessel, and a vessel that travels on land.

In another aspect, the invention provides an electronically accessibletag that includes a memory that includes maintenance data of a first anda second format where the first format is in accordance with an openstandard and the second format is in accordance with a closed standard.

Aspects of the invention can include one or more of the followingfeatures. The first format can be device independent. The maintenancedata can include maintenance procedures and technical specifications ofan article. The electronically accessible tag can include an input andoutput device for sending maintenance data and receiving updatedmaintenance data, and a processor and logic for updating the first andsecond format. Maintenance data of the first format can includemaintenance logs and maintenance data of the second format can includemaintenance procedures and technical specifications.

The invention can be implemented to realize one or more of the followingadvantages. By tagging one or more components of a complex article,technical information as well as repair, replacement, and/or maintenancerecords for the tagged components can be maintained separately fromother records and accessed directly on the component itself. Suchtagging greatly simplifies the handling of technical information andmaintenance, replacement and/or repair records for the complex article,and the tracking of component maintenance as the component moves fromlocation to location. For example, when an aircraft engine component isremoved from an airplane and a new engine component is substituted, themaintenance records for both engine components can remain physicallyjoined to the individual or respective components and accessible on thecomponents themselves. Moreover, each engine component retains a tagthat identifies the component, allowing an airline to track thecomponent as it moves from aircraft to aircraft. As another example,when an assembly line is retrofit with a new press, technicalinformation regarding the operation of the press can be stored directlyon the press itself (e.g., in a tag). Thus, when a new computer numericcontrol (“CNC”) component is provided to the press, technicalinformation regarding the interface between the CNC and the press can beretrieved from the tag on the press.

The tagging of complex articles can be implemented over a wide range ofscales. For example, an aircraft can be tagged, an aircraft engine onthe aircraft can be tagged, and a turbine of the aircraft engine can betagged. The type of computer-readable information stored on eachcomponent can be adjusted to the nature or operating environment of thecomponent. For example: the aircraft can be tagged with a uniqueidentifier; the aircraft engine can be tagged with a unique identifier,a log of flight time of the engine, and maintenance records of theengine; and the turbine can be tagged with a unique identifier and theresults of previous non-destructive evaluations of the integrity of theturbine.

Hierarchical and other relationships can be defined between or amongtracked components and can be used for tracking relationships betweencomponents. For example, an aircraft can be tagged with a tag thatidentifies one or more individual engines mounted to the aircraft duringa certain period of time.

Data for the tags can be received from sensors that sense a trait of thearticle. Data can also be input from specialized devices designed towrite to the component. For example: a tag on an aircraft can receive atime and data stamp from a writing device upon arrival at an airport; atag on an aircraft engine can receive the flight hours of the enginefrom a sensor that senses the operation of the engine; and a tag on theturbine can receive input from a specialized non-destructive evaluationunit after testing. Tags can also receive information from other datasources, such as, e.g., systems that provide circumstantial informationlike weather, traffic conditions, transportation schedules, and so on.

The system can be integrated with existing software and hardware systemsusing open interfaces. With such interfaces, the system is compatiblewith existing systems without the need for plug-ins or upgrades into theexisting systems. For example, the system can provide open interfaces tointegrate virtually every kind of tag, tag reader, scanner, sensor, andapplication. The system can be implemented to include applications thatcan generically read data from, and write data to, article tags. Thesystem can include generic tracking of real-time telemetry. The systemcan integrate existing geographical information systems (“GIS”) anddata.

The system can be integrated with existing software and hardware systemsusing closed interfaces. With such interfaces, the system is compatibleonly with systems that are licensed to use the closed interfaces. Such arestriction can prevent data from being accessed and changed by thosenot licensed to do so.

The system facilitates the scheduling and performance of maintenance ofmobile articles such as airplanes, ships, and trains. For example, thesystem helps an operator determine which maintenance can be completedwhen an airplane makes a temporary stop over. Furthermore, the systemdoes not need a central system to so facilitates maintenance because allthe necessary data in stored on the tags. A military vessel, such as anuclear submarine, operating at a remote locale thus need notcommunicate with a base to retrieve maintenance information and,advantageously, is able to maintain radio silence.

The details of one or more embodiments of the invention are set forth inthe accompanying drawings and the description below. Other features,objects, and advantages of the invention will be apparent from thedescription and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 shows an example of a complex article that is tagged.

FIG. 2 shows an example of a unique identification code.

FIGS. 3, 4, and 5 show examples of maintenance information that can bestored on a tag.

FIG. 6 shows another example of a complex article that is tagged.

FIG. 7 shows another example of maintenance information that can bestored on a tag.

FIG. 8 shows a method for maintaining a complex article.

FIG. 9 shows a system landscape for maintaining a complex article.

FIGS. 10 and 11 show methods for maintaining a complex article.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1 shows an example of a complex article, namely the tail of anaircraft 100, that is tagged. Aircraft 100 includes a body frame 105that supports an engine 110. Engine 110 is a component of aircraft 100and includes a compressor 115. Compressor 115 is a component of bothengine 110 and aircraft 100. Body frame 105, engine 110, and compressor115 are all tagged with electronically-accessible tags 120, 125, 130.

Tags 120, 125, 130 are electronically-accessible in that they store datain a machine-readable format. For example, tags 120, 125, 130 can storea computer-readable globally unique identifier (“GUI”). One suchglobally unique identifier is the Electronic Product Code (“ePC”) of theMIT (Massachusetts Institute of Technology) AutoID Center. FIG. 2illustrates the format of the ePC. Optionally, tags 120, 125, 130 canalso include a processor to process data. For example, tags 120, 125,130 can be smart cards or other devices that include a processor forprocessing information.

An interrogator (not shown) is a device for reading data from tags 120,125, 130. The interrogator may also write to tags 120, 125, 130. Tags120, 125, 130 can be, e.g., active and passive RFID tags, integratedcircuit (“IC”) microprocessor cards and memory cards, optical memorycards, barcodes, molecular tags, smart cards, or other computer-readablestorage devices that include information relating to the identificationof body frame 105, engine 110, and compressor 115, respectively. Theinterrogator can be any device capable of reading from tags 120, 125,130 such as, e.g., an optical scanner, a transceiver, a molecularreader, a card reader, a card-accepting device, or other device forreading data that can be interfaced with a computer.

Additionally, tags 120, 125, 130 can include a user-interface device.The user-interface device can be part of the tag or be a separate devicethat is coupled to the tag. Such a user-interface device can include,e.g., an input device for sending information to the tags 120, 125, 130and a display for displaying data read from tags 120, 125, 130. Anoperator can use a user-interface device to read data from tags 120,125, 130 without relaying the read data to remote locations, or withoutwriting additional information to tags 120, 125, 130.

Tags 120, 125, 130 can also store information related to the operation,maintenance, repair, replacement, and technical characteristics of therespective components to which they are attached (i.e., body frame 105,engine 110, and compressor 115). As shown in FIGS. 3, 4, and 5,information 300, 400, 500 can include operating environment informationassociated with the body frame 105, engine 110, and compressor 115. Inparticular, information 300 includes examples of operation records 305,maintenance records 310, and technical characteristics 315 relating toaircraft 100 that can be stored in tag 120 mounted to body frame 105.Information 300 also include information 320 that identifiesrelationships between aircraft 100, engine 110, and compressor 115. Forexample, information 320 can identify the hierarchical relationshipbetween aircraft 100 and components engine 110 and compressor 115 atdifferent times.

Likewise, information 400 includes examples of operation records 405,maintenance records 410, and technical characteristics 415 relating toengine 110 that can be stored in tag 125 mounted to engine 110, andinformation 500 includes examples of operation records 505, maintenancerecords 510, and technical characteristics 515 relating to compressor115 that can be stored in tag 130 mounted to compressor 115.

Information included in the technical characteristics 515, for example,can be: information describing procedures and technical specificationsfor performing preventive and corrective maintenance, the prerequisitesto performing the maintenance (for example, safety requirementsincluding safety tagging and electrical isolation, radiological controlsrequirements, and cleanliness requirements), and miscellaneousinformation describing the maintenance (such as the tools and equipmentneeded to do the maintenance, qualification of the operator or mechanicwho is going to do the maintenance, and the time needed to perform themaintenance). Alternatively, the described information can be storedelsewhere, such as within information 300, 400, 500.

A tag can also receive information from a sensor that senses a trait ofthe article or a component of the article. As shown in FIG. 6, anaircraft 600 includes a fuel level sensor 605 that measures the amountof fuel 610 in a fuel tank 615. Fuel tank 615 is a component of aircraft600 and is tagged with a tag 620 that receives information about theamount of fuel 610 from fuel level sensor 605 over a communication line625. Data from fuel level sensor 605 can be stored in raw form on tag620, or a processor can process the data from fuel level sensor 605 todetermine, e.g., the fuel consumed during a particular trip. Forexample, either tag 620 or sensor 605 can include such a processor. Theprocessed results can be stored on tag 620.

In order to identify when a trip has been completed or to receive otherinformation related to the operation, maintenance, repair, replacement,and technical characteristics of aircraft 600, tag 620 can also receiveinformation from sources other than fuel level sensor 605. For example,tag 620 can receive information over a communication line 630 from anantenna 635 mounted to aircraft 600. Antenna 635 can wirelessly receive,e.g., information about the current location of plane 600 and localweather conditions.

Information can be stored on the tags such as tags 120, 125, 130, 610 inopen formats, closed formats, or a combination of both. FIG. 7illustrates information 700 that is potentially stored on a tag, andcharacteristics of the format in which portions of information 700 arestored. In particular, information 700 includes operation records 705,maintenance records 710, and technical characteristics 715 that relateto a tagged article or a tagged component of an article. Operationrecords 705 and maintenance records 710 are stored in closed formats, asindicated by locked icons 715. Technical characteristics 715 are storedin open formats, as indicated by unlocked icons 720. Example openstandards include the rich text format (“RTF”), the extensible markuplanguage (“XML”) over the hypertext transfer protocol (“HTTP”), theportable document format (“PDF”) standard, the American Standard Codefor Information Interchange (“ASCII”), and post-script files. Examplesof closed standards include proprietary formats.

A tag can be mechanically coupled to a component by a variety of ways.For example, the tag can be coupled by using fasteners, adhesives,welding, or any combination thereof. Devices such as the describeduser-interface device and the sensor can be similarly coupled to thecomponent or the tag.

FIG. 8 shows an example of a method 800 for tracking, operating, andmaintaining a complex article using one or moreelectronically-accessible tags coupled to one or more components of thecomplex article. An interrogator performing method 800 first retrieves aGUI or other identifier that identifies a first component of the complexarticle (step 805). The identifier is retrieved from anelectronically-accessible tag that is coupled to the component. Theinterrogator can retrieve the ID, e.g., by optically or electronicallyscanning the tag.

The interrogator also retrieves maintenance information from the tag(step 810). The maintenance information can include, e.g., a historicalrecord of maintenance that has been performed on the component, ahistorical record of the past operation of the component, or informationrelated to procedures for maintaining the component. The information canbe stored in an open standard or in a closed standard.

If necessary, the retrieved maintenance information can be recorded sothat the information is made available separately from the tag (step815). For example, the retrieved maintenance information can be relayedto a central database system for storage or analysis. Recording theretrieved information separately from the tag creates a back-up copy ofthe maintenance information, and allows analyses that require increasedamounts of processing power or information from disparate informationsources to be performed. Examples of disparate information sourcesinclude multiple electronically-accessible tags coupled to thecomponents of a complex article, as well as multipleelectronically-accessible tags distributed throughout a fleet of complexarticles.

The interrogator, or a human user operating the interrogator, makes adecision as to whether or not a maintenance operation is to be performed(decision 820). The maintenance operation can be performed on the taggedcomponent, or on another component of the article. The decision can bebased on the time since the last maintenance operation was performed,the operational history of the component, or combinations of these andother factors. The decision can be based on the service hours of acomponent. The decision can also be based on information from disparate,multiple, electronically-accessible tags.

If it is decided to perform the maintenance operation, then instructionsfor performing the maintenance operation can be retrieved from theelectronically-accessible tag, if needed (step 825). For example, thevolume of oil that lubricates an engine can be retrieved from a tagmounted to the engine. This capability minimizes the chance thatmaintenance is delayed while maintenance instructions are located, orthat incorrect maintenance instructions are inadvertently used. Themaintenance operation can then be performed (step 830). The performancecan be based on the retrieved instructions, as appropriate.

A second decision is made as to whether the last component of thearticle has been interrogated, or if the interrogation is to end(decision 835). This decision can be made by a user, or it can be madeby the interrogator or other processing system based on information thatidentifies a relationship between one or more components of an articleand the article itself, and/or one or more components of a component andthe component itself. If it is decided that the last component has beeninterrogated, then method 800 ends.

Alternatively, if it is decided that additional components are to beinterrogated, then the interrogator retrieves a GUI or other identifierthat identifies another component of the complex article (step 840) andagain retrieves maintenance information regarding the next component anddecides whether maintenance is necessary.

Maintenance information need not be retrieved from the same componentupon which a maintenance operation is performed, or from whichmaintenance instructions are retrieved. For example, informationrelating to the fuel usage of an engine in a single engine motor vehiclecan be retrieved from an electronically-accessible tag on a fuel tank,while instructions for adjusting the operation of an engine can beretrieved from an electronically-accessible tag on the body frame.

The following describes an example implementation of method 800.Aircraft 100 described above is flying from Frankfurt to San Franciscowith a two-hour stop over in Washington D.C. As the aircraft 100 landsin Washington D.C., an operator, such as an engine mechanic, who isresponsible for maintenance of the aircraft can interrogate tag 125 todetermine which, if any, preventive maintenance can be performed onengine 110 during the two-hour stop over. The operator can use aninterrogator such as the one described above or, alternatively, caninterface with tag 125 through a user-interface device that is coupledto or included with tag 125. Tag 125 includes information that specifyall preventive maintenance for engine 110. The information can, forexample, specify the preventive maintenances that have not beenperformed for the current maintenance cycle and are due. The operatorprovides information that specify resources available to perform themaintenance. Such information can include the qualification of themechanic, the maintenance equipment locally available to perform themaintenance, as well as any time constraints such as the two-hour limit.Such information can be stored in the interrogator. Using informationstored on tag 125 and information provided by the operator, tag 125determines which preventive maintenance, if any, can be performed duringthe stop over and presents these maintenance options to the operator.Alternatively, the interrogator can retrieve maintenance informationfrom tag 125, make the determination, and present the options to theoperator. In response to a selection from the operator, the tag providesthe appropriate procedures and technical specifications for performingthe selected maintenance. When the operator completes the maintenance,the operator stores a record of the maintenance completion in tag 125.

As shown in FIG. 9, a system landscape 900 can include multiple,independent systems using methods and apparatus, including computerprogram products, for maintaining a complex article in accordance withthe invention. In particular, system landscape 900 includes a tag 905, acollection of interrogators 910, 915, 920, 925, and a collection ofsystems 930, 935, 940, 945. Tag 905 is coupled to a component 950 of acomplex article 955 and can store information that identifies tag 905,as well as maintenance records, operational records, and technicalcharacteristics of component 950 and/or complex article 955.

Interrogator 910 and system 930 are operated by a manufacturer ofcomplex article 955 or a manufacturer of component 950. Interrogator 910can write to tag 905. System 930 contains information and instructionsrelating to the maintenance of component 950 and/or complex article 955,and for providing component 950 with an identifier. For example, system930 can include a database that stores technical information about theoperation and maintenance of component 950 and instructions forperforming maintenance operations on component 950.

Interrogator 915 and system 935 are operated by a distributor of complexarticle 955 or component 950. Interrogator 915 can read from tag 905.System 935 contains information relating to the distribution ofcomponent 950 and/or complex article 955. For example, system 950 caninclude a database that includes information relating to the location ofcomponent 950 as it moves through a distribution system.

Interrogator 920 and system 940 are operated by an operator of complexarticle 955 that includes component 950. Interrogator 920 can write toand read from tag 905. System 940 contains information and instructionsrelating to the maintenance of component 950 and/or complex article 955,and for tracking component 950 as it changes locations during operation.For example, system 940 can include a database that stores informationabout the performance of maintenance operations upon component 950, theoperational records of component 950, as well as operational records,maintenance records, and location records of other components.

Interrogator 925 and system 945 are operated by a maintainer of taggedcomponent 950 and/or complex article 955. Interrogator 925 can write toand read from tag 905. System 945 contains information and instructionsrelating to the maintenance of component 950 and/or complex article 955,and for tracking component 950 as it changes locations during operation.For example, system 945 can include a database that stores informationabout the performance of maintenance operations upon component 950, theoperational records of component 950, as well as operational records,maintenance records, and location records of other components.

Any of the roles described above need not be present in a systemlandscape in accordance with the invention. For example, a manufacturercan also distribute tagged component 950, or an operator can alsomaintain tagged component 950 or complex article 955. Furthermore,additional roles not described above can be included in the systemlandscape. For example, a retailer can transfer the complex article fromthe distributor to the operator, more than one operator can operate asingle tagged component 950 or complex article 955, or more than onemaintainer can maintain a single tagged component 950 or complex article955.

Complex article 955 can include more than one component and more thanone component tag. In this case, complex article 955 can include ageneral tag. The general tag includes information that describe thecomplex article as a whole. Such information can include a hierarchy ofthe components of complex article 955. For example, the information canspecify that one component is part of another component. Suchinformation can also include maintenance information for the complexarticle as a whole. For example, the general tag can include a log ofcomponent replacement and, furthermore, can identify a particularcomponent even when the particular component and its tag has beenremoved from complex article 955. The general tag can also include logicand data for and managing and prioritizing the maintenance of allcomponents of complex article 955. For example, the logic and data canspecify that maintenance on a vital component is more important toperform than maintenance on a non-vital component. Alternatively, allinformation included in the general tag can be stored on component tags.A component tag can include information that describes all or part ofthe component hierarchy.

FIG. 10 shows an example method 1000 by which systems 930, 935, 940, 945interact with a tag such as tag 905. During the performance of method1000, manufacturer system 930 writes a globally unique identifier to tag905 (step 1005) and technical information about the component to tag 905(step 1010). The GUI and technical information can be written after orbefore tag 905 is mounted to the component. For example, the GUI andtechnical information can be written to tag 905 g in a read-only formatduring manufacture of tag 905. The GUI and technical information can bewritten, e.g., in an open standard.

At some point the manufacturer transfers the tagged component to adistributor. The tagged component can be provided as a stand aloneelement, or as a component of an assemblage of components such as acomplex article. Distributor system 935 reads tag 905 and identifies thecomponent from the GUI (step 1015). Distributor system 935 recordslocation information that identifies the location of tag 905, and hencethe location of the tagged component (step 1020).

The distributor can now move and track the tagged component through adistribution system. For example, the distributor can move the taggedcomponent from a central warehouse to a regional distribution center. Totrack tag 905, distributor system 935 again reads the GUI from tag 905(step 1025) and records location information that identifies thelocation of tag 905 and the tagged component (step 1030). If the GUI isin an open standard, then the distributor need not require specializedequipment or licenses to track the component in the distribution system.

At some point the distributor transfers the tagged component to anoperator. The tagged component can be provided as a stand alone element,or as a component of an assemblage of components such as a complexarticle. Operator system 940 reads tag 905 and identifies the componentfrom the GUI (step 1035). Operator system 940 records locationinformation that identifies the location of tag 905, and hence thelocation of the tagged component (step 1040). Operator system 940 canrepeatedly read the GUI from tag 905 and record location information totrack the tagged component as it moves through an operation system. Forexample, operator system 940 can track the location of a tagged aircraftengine as it moves from plane to plane, and from airport to airport.

Operator system 940 can also read technical information about thecomponent from tag 905 (step 1045) and apply the read technical info asappropriate (step 1050). For example, operator system 940 can read thetechnical characteristics of the component from the tag to determine ifthe component is compatible with other components in a complex article.

At some point, the operator of the tagged component will place thetagged component in service. Operation records describing the nature ofthe service can be written to tag 905. For example, as discussed above,a sensor that is mounted to the component, or another component of acomplex article, can write records to tag 905. Alternatively, operatorsystem 940 can write operation records to tag 905 (step 1055). Forexample, operator system 940 can write the identities or characteristicsof other components in a complex article to tag 905. Operator system 940can write also write other operation records, such as, e.g., locationinformation or performance information, to tag 905.

The operation records can be written by operator system 940 using aclosed standard. This can prevent others from accessing or changing theoperational records of the tagged component without the authorization ofthe operator.

Operator system 940 can also read operation records about the operationof the tagged component from tag 905 (step 1060) and apply the readoperation records as appropriate (step 1065). For example, operatorsystem 940 can apply the read operation records to retrieve sensormeasurements to determine the operational behavior of the taggedcomponent or to compare the operational behavior of the taggedcomponents to the expected operational behavior. Operator system 940 canalso apply the read operation records to determine when maintenance ofthe tagged component is needed.

At some point, the operator will transfer the tagged component to amaintainer. For example, an airline that operates an aircraft with atagged engine can allow a maintenance organization to inspect andmaintain the aircraft. Maintainer system 945 reads tag 905 andidentifies the component from the GUI (step 1070). Maintainer system 945can also read technical information about the component from tag 905(step 1075) and apply the read technical info as appropriate (step1080). For example, maintainer system 945 can read instructions formaintaining the tagged component from tag 905, and display theinstruction for use in performing a maintenance operation.

Maintainer system 945 can also read operation records about theoperation of the tagged component from tag 905 (step 1085) and apply theread operation records as appropriate (step 1090). For example,maintainer system 945 can apply the read operation records to determinewhen maintenance of the tagged component is needed and the type ofmaintenance operation that is to be performed. Maintainer system 945 canapply the read operation records by, e.g., displaying the operationrecords to a user who makes a decision as to whether maintenance isnecessary or by relaying the operation records to a processor that makesa maintenance decision based on predetermined rules.

Maintainer system 945 can also write maintenance records to tag 905(step 1092). For example, maintainer system 945 can write the date thata certain maintenance operation has been performed, or the results of amaintenance or inspection operation. The maintenance records can bewritten by maintainer system 945 using a closed standard. The closedstandard can be shared with others as desired. For example, an operatorand one or more maintainers can use a common closed format for operationand maintenance records. This can prevent others from accessing andchanging the maintenance records of the tagged component without theauthorization of the operator and/or the maintainer.

Maintainer system 945 can also read maintenance records about themaintenance of the tagged component from tag 905 (step 1094) and applythe read maintenance records as appropriate (step 1096). For example,operator system 940 can apply the read maintenance records to determinewhen maintenance or inspection of the tagged component is needed and thetype of maintenance or inspection operation that is to be performed.Maintainer system 945 can apply the read maintenance records by, e.g.,displaying the maintenance records to a user who makes a decision as towhether maintenance is necessary or by relaying the maintenance recordsto a processor that makes a maintenance decision based on predeterminedrules or artificial intelligence approaches.

As discussed above, when the complex article includes more than onecomponent and more than one component tag, either the component tags ora general tag can include information that describes the complex articleas a whole. An interrogator can thus retrieve such information fromeither a general tag or a component tag.

FIG. 11 shows an example method 1100 by which a company or other entitycan profit from the maintenance of a complex article that includes atagged component. In particular, an entity can select an open, publicformat for the storage of information upon a tag (step 1105). The entitycan also develop a closed standard for the storage of information uponthe tag (step 1110). The entity can also define which information is tobe stored in the selected open format upon the tag, and whichinformation is to be stored in the closed standard upon the tag (step1115). The definition can be performed by the entity itself, or inconjunction with a manufacturer of the component that is to be tagged.The results of the definition can reflect a need for securing certaininformation. For example, the definition can define that identifyinginformation is to be stored in an open format, while maintenance recordsare to be stored in a closed format to prevent unauthorized users fromreading and writing maintenance records.

The entity can also arrange for the manufacture of a tag with thedefined open and closed formats and information, as well as the couplingof the tag to a component of a complex article (step 1120). The entitycan arrange for the manufacture by, e.g., manufacturing the tag itselfor by licensing a design to a tag manufacturer. Similarly, the tag canbe coupled to the component by the entity, a tag manufacturer, or acomponent manufacturer.

The entity can also license the closed standard for data to an operatorof the complex article (step 1125). The license, for example, can allowall maintenance employees of the operator to use the standard.

The entity can also license the closed standard for data to one or moremaintainers of the complex article (step 1130). In this case, thelicense can be sold to the businesses that the operator of the complexarticles has employed to perform the maintenance.

By licensing the closed standard to operators and/or maintainers, theentity can receive an income stream even when no new tag purchases aremade. Moreover, since tags can be designed to be robust and survive formany years, the income stream can be used to offset the cost of thecapital investment in the tags.

The invention can be implemented in digital electronic circuitry, or incomputer hardware, firmware, software, or in combinations of them. Theinvention can be implemented as a computer program product, i.e., acomputer program tangibly embodied in an information carrier, e.g., in amachine-readable storage device or in a propagated signal, for executionby, or to control the operation of, data processing apparatus, e.g., aprogrammable processor, a computer, or multiple computers. A computerprogram can be written in any form of programming language, includingcompiled or interpreted languages, and it can be deployed in any form,including as a stand-alone program or as a module, component,subroutine, or other unit suitable for use in a computing environment. Acomputer program can be deployed to be executed on one computer or onmultiple computers at one site or distributed across multiple sites andinterconnected by a communication network.

Method steps of the invention can be performed by one or moreprogrammable processors executing a computer program to performfunctions of the invention by operating on input data and generatingoutput. Method steps can also be performed by, and apparatus of theinvention can be implemented as, special purpose logic circuitry, e.g.,an FPGA (field programmable gate array) or an ASIC (application-specificintegrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read-only memory ora random access memory or both. The essential elements of a computer area processor for executing instructions and one or more memory devicesfor storing instructions and data. Generally, a computer will alsoinclude, or be operatively coupled to receive data from or transfer datato, or both, one or more mass storage devices for storing data, e.g.,magnetic, magneto-optical disks, or optical disks. Information carrierssuitable for embodying computer program instructions and data includeall forms of non-volatile memory, including by way of examplesemiconductor memory devices, e.g., EPROM, EEPROM, and flash memorydevices; magnetic disks such as internal hard disks and removable disks;magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor andthe memory can be supplemented by, or incorporated in special purposelogic circuitry.

To provide for interaction with a user, the invention can be implementedon a computer having a display device such as a CRT (cathode ray tube)or LCD (liquid crystal display) monitor for displaying information tothe user and a keyboard and a pointing device such as a mouse or atrackball by which the user can provide input to the computer. Otherkinds of devices can be used to provide for interaction with a user aswell; for example, feedback provided to the user can be any form ofsensory feedback, such as visual feedback, auditory feedback, or tactilefeedback; and input from the user can be received in any form, includingacoustic, speech, or tactile input.

A number of embodiments of the invention have been described.Nevertheless, it will be understood that various modifications may bemade without departing from the spirit and scope of the invention. Forexample, the steps of the invention can be performed in a differentorder and still achieve desirable results. Accordingly, otherembodiments are within the scope of the following claims.

1. A method for storing maintenance information on anelectronically-accessible tag that is coupled to an article, the methodcomprising: storing first maintenance information in a first format andsecond maintenance information in a second format in theelectronically-accessible tag, the first format being open to generalaccess and the second format being closed to general access.
 2. Themethod of claim 1, wherein the first format is device independent. 3.The method of claim 1, wherein the first format is in accordance withone of RTF, ASCII, and PDF.
 4. The method of claim 1, wherein the secondformat is proprietary and can only be accessed by proprietary devices.5. The method of claim 1, further comprising: retrieving at least one ofthe first maintenance information and the second maintenanceinformation; updating a format of the retrieved maintenance information;and storing the retrieved maintenance information with an updated formatin the electronically-accessible tag.
 6. The method of claim 1, whereinat least one of the first maintenance information and the secondmaintenance information comprises maintenance procedures and technicalspecifications related to the article.
 7. The method of claim 1, whereinstoring the first maintenance information and the second maintenanceinformation includes: storing a first type of maintenance information inthe first format; and storing a second type of maintenance informationin the second format.
 8. The method of claim 7, wherein the first typeof maintenance information comprises maintenance logs; and the secondtype of maintenance information comprises maintenance procedures andtechnical specifications.
 9. The method of claim 1, wherein at least oneof the first maintenance information and the second maintenanceinformation comprises maintenance information regarding a component ofone of an aircraft, a sea going vessel, and a vessel that travels onland.
 10. The method of claim 1, wherein the first maintenanceinformation comprises a maintenance instruction.
 11. The method of claim1, wherein the second information comprises an inspection record. 12.The method of claim 1, wherein the second maintenance informationcomprises a date when maintenance was performed.
 13. The method of claim1, wherein storing first maintenance information and second maintenanceinformation comprises: storing first maintenance information and secondmaintenance information about components of a complex article in aplurality of electronically-accessible tags that are coupled to thecomponents.
 14. An electronically-accessible tag, comprising: memorythat comprises first maintenance data of a first format and secondmaintenance data of a second format, the first format being open togeneral access and the second format being closed to general access, theelectronically-accessible tag being coupled to an article.
 15. Theelectronically-accessible tag of claim 14, wherein the first format isdevice independent.
 16. The electronically-accessible tag of claim 14,wherein the first format is in accordance with one of RTF, ASCII, andPDF.
 17. The electronically-accessible tag of claim 14, wherein thesecond format is a proprietary format.
 18. The electronically-accessibletag of claim 14, wherein at least one of the first maintenance data andthe second maintenance data comprises maintenance procedures andtechnical specifications of the article.
 19. Theelectronically-accessible tag of claim 14, further comprising: an inputand output device for sending first maintenance data and secondmaintenance data and for receiving updated maintenance data.
 20. Theelectronically-accessible tag of claim 14, further comprising: aprocessor and logic for updating the first format and the second format.21. The electronically-accessible tag of claim 14, wherein: firstmaintenance data of the first format comprises maintenance logs; andsecond maintenance data of the second format comprises maintenanceprocedures and technical specifications.
 22. Theelectronically-accessible tag of claim 14, wherein: the articlecomprises one of an aircraft, a sea going vessel, and a vessel thattravels by land; and the first maintenance data and the secondmaintenance data comprises maintenance data of one or more components ofthe aircraft, sea going vessel, or vessel that travels by land.
 23. Theelectronically-accessible tag of claim 14, wherein the first maintenancedata comprises a maintenance instruction.
 24. Theelectronically-accessible tag of claim 14, wherein the secondmaintenance data comprises an inspection record.
 25. Theelectronically-accessible tag of claim 14, wherein the secondmaintenance data comprises a date when maintenance was performed.